chore: bump root pnpm to 11.1.2#76
Conversation
efec967 to
142e535
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 36b22c0fac
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
36b22c0 to
f75a33f
Compare
|
I haven't looked into the reason but upgrading to pnpm v11 makes the |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f75a33f8af
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…nd approve native builds The `file:../../babel` references in the 4 benchmark packages trigger a pnpm 11 crash during the lifecycle re-import step (pnpm/pnpm#11663 / pnpm/pnpm#11662, still in draft). Aligning with the other plugins' `workspace:*` pattern sidesteps the bug; benchmarks must now run after `pnpm build`, same as every other workspace plugin. Also fills in the `allowBuilds` template pnpm 11 prompts for, allowing `@swc/core` (native bindings for benchmarks) and `playwright-chromium` (Chromium download for examples e2e).
f75a33f to
2a49a2a
Compare
Summary
packageManagerpin topnpm@11.1.2package.jsononlyTesting